Drop Payee Check Constraint #3287
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Set all null lease payment statuses to their correct value based on the lease term's payment amount + GST
Set all null lease payment statuses to their correct value based on the lease term's payment amount + GST
dfilteau
requested review from
devinleighsmith,
asanchezr,
FuriousLlama,
stairaku,
PryancaJSharma,
eddherrera and
buddy326
as code owners
|
✅ No secrets were detected in the code. |
|
✅ No secrets were detected in the code. |
|
✅ No secrets were detected in the code. |
FuriousLlama
approved these changes
Jun 27, 2023
|
✅ No secrets were detected in the code. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PIMS_ACQUISITION_PAYEE table's ACQPAY_COMP_REQ_PAYEE_TCC check constraint has multiple, parentheses-separated conditions to ensure that there are NONE or ONE payee. Unfortunately, SQL Server strips out all parentheses and then prioritizes ANDs over ORs in the check constraint, resulting in unpredictable results.
The check constraint is being dropped until a better solution is found.